Monitoring Windows Services
Nodinite empowers you to monitor, manage, and optimize Windows Services across your infrastructure. Instantly discover all services, automate health checks, and provide secure, role-based access for your team.
✅ Instantly discover and monitor all Windows Services
✅ Set custom thresholds and receive real-time alerts for service health and uptime
✅ Share access to selected services with end-users for secure self-service
✅ Actionable alerts and Remote Actions within role-based Monitor Views to resolve issues fast

Example list of monitored 'Windows Services' as resources in a Monitor View.
Diagram: Windows Server monitoring architecture showing WMI-based health checks from the Agent to local and remote servers, and status reporting to Nodinite Web Client.
Monitoring Features
- The Nodinite Windows Server Monitoring Agent uses WMI to automatically discover all Windows Services. Sharing insights is easy with Monitor Views.
- State Evaluation – Ensure Windows Services are up and running with user-defined thresholds.
- Category-based monitoring – Group monitored Resources by Categories for streamlined management.
State evaluation for Windows Services
Nodinite displays each monitored Windows Service as a Resources. For example, if you have 2 Windows Server configurations with 150 and 270 Windows Services, you will have 420 'Windows Service' resources in Nodinite.
The Resources name matches the Windows Service name in the format
Display Name <Service Name>.The 'Windows Service' resource belongs to the following Category:
Category Description Windows Service Ensure Windows Services are up and running 
List of the Windows Service category as a filter in a Monitor View.The Application name is the Display Name from the configuration of the monitored Windows Server:

Example of the Application path for a monitored Windows Service resource.
Each item (presented in Nodinite as a Resource) is evaluated with a state: OK, Warning, Error, or Unavailable.
You can reconfigure state evaluation at the Resources level using the Expected State feature.
Note
Depending on the user-defined synchronization interval for the Windows Server Monitoring Agent, there may be a delay before Nodinite Web Client/Monitor Views reflect changes. Click Sync All (or use the dropdown for individual agent selection) to force a resynchronization.

Option to force Nodinite to request a resynchronization with the monitoring agent.
Monitoring Windows Services
For the Windows Service category, Nodinite evaluates the monitored state as described below:
| State | Status | Description | Actions | |
|---|---|---|---|---|
| Unavailable | Service not available | The server can't be reached or evaluated due to network or security issues Bad configuration (invalid/non-existing Windows Service) |
Review prerequisites | |
| Error | Error state raised | The 'Windows Service' is NOT running | Play Stop Restart Edit Details |
|
| Warning | Warning state raised | Not implemented | - | |
| OK | Online | The 'Windows Service' is up and running | Play Stop Restart Edit Details |
Actions for Windows Service
The following Remote Actions are available for the Windows Service Category:

Available remote actions for the Windows Service category.
Start
Start a stopped Windows Service by clicking the Action button and selecting Start in the 'Control Center' section.

Enable Windows Service using the 'Enable' action.
You will be prompted to confirm the operation:

Example of the 'Enable' prompt.
A modal will present the result of the operation:

Example of a successful start operation.
Stop
Stop a running Windows Service by clicking the Action button and selecting Stop in the 'Control Center' section.

Stop Windows Service using the 'Stop' action.
You will be prompted to confirm the operation:

Example of the 'Stop' prompt.
A modal will present the result of the operation:

Example of a successful stop operation.
Restart
Restart an enabled Windows Service by clicking the Action button and selecting Restart in the 'Control Center' section.

Stop and start the Windows Service using the 'Restart' action.
You will be prompted to confirm the operation:

Example of the 'Restart' prompt.
A modal will present the result of the operation:

Example of a successful restart operation.
Details
View comprehensive details and perform operations on any Windows Service resource by clicking the Action button and selecting Details in the 'Control Center' section.

Open details modal using the 'Details' action.
Next, click the option to present the modal.

Example of the 'Details' modal.
What you can do in the Details modal:
- View Service Information - See service name, display name, description, path, startup type, and log-on account (read-only)
- Start - Start a stopped Windows Service directly from the details view
- Stop - Stop a running Windows Service directly from the details view
- Restart - Restart a Windows Service directly from the details view
- View Dependencies - See service dependency relationships in both directions
The details modal provides the same information as the Edit modal, with all fields being read-only, plus convenient action buttons for service control.
In the Dependencies tab, you can view the complete dependency chain for the Windows Service:
- System components this service depends on - Services required for this service to start and run
- System components that depend on this service - Services that require this service to be running

Dependencies for a Windows Service showing both upstream and downstream relationships.
Edit
Change the startup type for any Windows Service resource by clicking the Action button and selecting Edit in the 'Control Center' section.

Edit Windows Service using the 'Edit' action.
Next, click the option to present the modal.
What you can do in the Edit modal:
- View Service Information - See service name, display name, description, path, startup type, and log-on account (read-only)
- Change Startup Type - Modify how and when this service will start
- Save Changes - Click Save to persist the startup type configuration
The edit modal displays the same information as the Details modal, with the startup type field being editable.
Configuration
Use Remote Configuration to manage Windows Service configuration.
Windows Services tab
Click the Windows Services tab to manage Windows Service monitoring options.

Example of the 'Windows Services' tab.
- Enable Windows Services Monitoring – When checked, Windows Services are monitored for this Windows Server
Windows Services General Tab
Click the Windows Services General tab to manage monitoring options.

Example of the 'Windows Services General' tab.
- Polling Interval of Windows Services – Polling interval in seconds
Windows Services Source Tab
Click the Source tab to manage include options.

Example of the 'Windows Services Source' tab.
- Include Disabled Services – When checked, Windows services with startup type 'disabled' are monitored
- Include Manual Services – When checked, Windows services with startup type 'manual' are monitored
Windows Services Options Tab
Click the Options tab to manage exclude options.

Example of the 'Windows Services Options' tab.
You can add multiple RegEx expressions to exclude Windows Services from monitoring by Service Name and/or Display Name.
- Service Name Filter – Exclude Windows service(s) matching the provided RegEx expression
- Display Name Filter – Exclude Windows service(s) matching the provided RegEx expression
Tip
A common exclusion filter is:
(Sync\sHost|CDPUserSvc)_([0-9a-fA-F]*)
Next Step
Related Topics
Monitor Views
Monitoring
Resources
Windows Server Monitoring Agent
